UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

Symantec ProxySG providing user authentication intermediary services using PKI-based user authentication must implement a local cache of revocation data to support path discovery and validation in case of the inability to access revocation information via the network.


Overview

Finding ID Version Rule ID IA Controls Severity
V-94297 SYMP-AG-000420 SV-104251r1_rule Medium
Description
Without configuring a local cache of revocation data, there is the potential to allow access to users who are no longer authorized (users with revoked certificates). The intent of this requirement is to require support for a secondary certificate validation method using a locally cached revocation data, such as Certificate Revocation List (CRL), in case access to OCSP (required by CCI-000185) is not available. Based on a risk assessment, an alternate mitigation is to configure the system to deny access when revocation data is unavailable. This requirement applies to ALGs that provide user authentication intermediary services (e.g., authentication gateway or TLS gateway). This does not apply to authentication for the purpose of configuring the device itself (device management).
STIG Date
Symantec ProxySG ALG Security Technical Implementation Guide 2019-05-21

Details

Check Text ( C-93483r1_chk )
Verify that PKI Certificate Revocation Lists have been configured.

1. Log on to the Web Management Console.
2. Browse to Configuration >> SSL >> CRLs.
3. Verify that at least one CRL has been defined.

If Symantec ProxySG providing user authentication intermediary services using PKI-based user authentication does not implement a local cache of revocation data to support path discovery and validation in case of the inability to access revocation information via the network, this is a finding.
Fix Text (F-100413r1_fix)
Configure PKI Certificate Revocation lists.

1. Log on to the Web Management Console.
2. Browse to Configuration >> SSL >> CRLs.
3. Click "New" and configure in accordance the setting required by site guidance.